ci: skip release-automation chore commits in generated release notes#332
Merged
Conversation
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
Owner
Author
|
Successfully created backport PR for |
Vulthil
added a commit
that referenced
this pull request
Jul 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The v1.1.0 release notes included the release machinery's own housekeeping commits under Miscellaneous ("Mark public API shipped for v1.0.0", "Bump version to 1.1.0", "Validate packages against the 1.0.2 baseline") - these recur every release cycle, so each release inherits the previous one's process noise. This adds skip parsers for the three automation-authored commit patterns, anchored to the exact commit-message templates in release.yml and version-bump.yml, placed above the generic ^chore parser (git-cliff parsers are first-match-wins).
Genuine chore/ci commits (hand-written changes) still appear; dependabot bumps stay under Build & Dependencies.
Verification
Backport to v1.0: yes (label) - release notes generate from the releasing branch's cliff.toml; a future advisory-driven 1.0.x release produces the same automation commits.